home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 24
/
Aminet 24 (1998)(GTI - Schatztruhe)[!][Apr 1998].iso
/
Aminet
/
biz
/
p5
/
68060_V43_1c.lha
/
CyberGuard
/
CyberGuard.doc
< prev
next >
Wrap
Text File
|
1998-02-05
|
2KB
|
46 lines
CyberGuard is offering the same functionality and more for
the 060 what Enforcer V37 provides for the 68030 and 68040.
It supports almost every option Enforcer V37 offers so the
usage is almost the same.
As I'm born as a lazy guy i only desribe the differences
to Enforcer. For the other options please look into the
Enforcer V37 manual.
Enforcer V37 was written by M.Sinz and the original Enforcer
idea was developed by Bruce Nesbitt that i want to thank here.
o Well..some people may have heard about the mysterious program
Guardian Angel that was hinted by a comment "Angel Hit"
somewhere in the 2.x Release-Notes.
Well..some people may also have seen this program but i know
nobody that has seen it working:-)
The program should have been able to writeprotect the
free memory to find these annoying random write bugs you
can search weeks for.
The option GUARD activates this mode so hits to free memory
are caught. There's a speed limitation in this mode that
allows Cyberguard to protect only memory pages that are
complete in the free memory to avoid writeprotecting data
areas of programs.
Beware!!!! After activating this option your machine CRAWLS.
o Another difference to Enforcer V37 is that Cyberguard can
show the instruction that caused a hit by the option
SHOWDISS. With the option DISSLINES you determine the amount
of instructions after the hit causing instruction should be
displayed.
o NOZERO disables the Zeropage MMU-protection.
This option makes only sense for me during debugging.
o FSPACE,VERBOSE have no meaning right now.
My startup-sequence entry:
run >NIL: segtracker
run >NIL: cyberguard STACKLINES=8 SHOWDISS FILE=CNC:0/0/640/100/CyberGuard/Auto/Close
Instead of CNC: use the console you're like.
Ralph Schmidt